Member Sign In
Not a member?

A Wired.com user account lets you create, edit and comment on Webmonkey articles. You will also be able to contribute to the Wired How-To Wiki and comment on news stories at Wired.com.


It's fast and free.

Sign in with OpenID
Sign In
Webmonkey is a property of Wired Digital.
processing...
Join Webmonkey

Please send me occasional e-mail updates about new features and special offers from Wired/Webmonkey.
Yes No

Please send occasional e-mail offers from Wired/Webmonkey affiliated web sites and publications, and carefully selected companies.
Yes No

I understand and agree that registration on or use of this site constitutes agreement to Webmonkey's User Agreement and Privacy Policy.
Webmonkey is a property of Wired Digital.
processing...

Retrieve Sign In

Please enter your e-mail address or username below. Your username and password will be sent to the e-mail address you provided us.

or
Webmonkey is a property of Wired Digital.
processing...

Welcome to Webmonkey

A private profile page has been created for you.
As a member of Webmonkey, you can now:
  • edit articles
  • add to the code library
  • design and write a tutorial
  • comment on any Webmonkey article
Close
Webmonkey is a property of Wired Digital.

Sign In Information Sent

An e-mail has been sent to the e-mail address registered in this account.
If you cannot find it in your in-box, please check your bulk or junk folders.
Sign In
Webmonkey is a property of Wired Digital.

Adobe Announces Photoshop for the ‘Droids

With Friday’s launch of the the new Motorola Droid and some slick new features in Android 2.0, Google’s mobile operating system is stealing a bit of thunder from the iPhone.

Now, there’s one more battleground: Photoshop.com, Adobe’s online photo service based around its flagship photo editor, has jumped on the Android bandwagon as well. Adobe released a new Android-based photo app Friday that allows you to edit, view, share and upload images directly from your phone. It works with any photos stored on the phone.

Photoshop.com Mobile is already available for the iPhone and Windows Mobile devices. It’s a free download on all three mobile platforms. The Android version of Photoshop.com Mobile has all the features found in its Apple-y and Microsoft-y cousins, but it also packs in a few things that can’t be done on the iPhone — like background image uploads, so you can upload an album and still do other things with the images are being transferred.

As for the editing tools themselves, well… don’t expect “real” Photoshop. But the basic options like cropping, straightening, color corrections and preset image transformations can go a long way toward making your mobile images look much better.

Adobe has a video overview, but for some reason doesn’t offer any way to embed it. You can check it out on the Photoshop.com Mobile site. Watch for the subtle iPhone snub about midway through the video, when Adobe’s Corey Barker says, “this particular phone has a really cool feature called background processing…”

If you’d like to give the new Photoshop.com Mobile for Android app a try, head to the Android marketplace.

See Also:



After 5 Years on Web, Firefox Preps for Next Round

Firefox team
From left to right, Mozilla’s director of mobile Stuart Parmenter, director of Firefox development Mike Beltzner, manager of Firefox’s front-end–features team Johnathan Nightingale and Firefox principal engineer Vladimir Vukićević. The foursome sits below a quilt made by Mozilla Foundation chairwoman Mitchell Baker. Photo: Michael Calore

 

MOUNTAIN VIEW, California — Vladimir Vukićević was working at the Mozilla office when Firefox was first released into the wild.

“All of our servers melted instantly,” Vukićević says. “We spent an hour trying to get the downloads back up.”

Indeed, the anticipation around the release of Firefox 1.0 on November 9, 2004 — five years ago Monday — was electric.

Mozilla had already produced its own eponymous browser based on open source code in 2002, but it was largely considered a failure. Firefox was the organization’s great re-do, and its second attempt to unseat its biggest nemesis, Microsoft Internet Explorer.

A half-decade later, Firefox is no longer a scrappy upstart but a dominant player. Old rival IE still commands around 60 percent of the market share, but close to a quarter of the web now uses Firefox — a formidable number which speaks to its success as an open source project. At a time when nobody wanted to go toe-to-toe with Microsoft, thousands of disparate programmers rose to the challenge, landing Firefox on the short list of other open source triumphs like Wikipedia, Ubuntu Linux, WordPress and the web itself.

Successes aside, Firefox is now at a tipping point.

Five years ago, it was all about beating Microsoft. Left unchecked, the company was free to dictate what shape the web would take. Firefox’s popularity created a new market for web standards and forced Redmond to take open-web technologies seriously.

Now, Firefox faces a bigger struggle. It needs to continue to innovate and remain relevant in an ever-changing, and ever-more-competitive, landscape.

“When it was just us and Microsoft, the story was very simple — it was the little guy versus the giant,” says Mozilla’s Mike Beltzner, who oversees Firefox’s development. “Now you’ve got heavy hitters like Microsoft, Google and Apple all competing, which make the stories a lot more interesting.”

The web itself has changed significantly in the last five years, as well. It’s no longer just a network of connected documents, but a full-fledged platform filled with real applications that run in the browser and share data with one another.

“It’s hard to cast your mind back and think about what the internet was like in 2004,” says Beltzner. “Five years ago, there was no Google Maps. Gmail was very new. All these things — applications that are now parts of the web that we would never think couldn’t be there — were just not there. Most of the reason was that browsers weren’t yet being designed with all of these advanced capabilities.”

Firefox was one of the first browsers built for this new web filled with applications. As a result, it gained favor with developers and users. But it also encouraged fiercer competition.

“It’s not just that the platform has changed, there’s a whole ecosystem of great browsers now,” says Mozilla’s Johnathan Nightingale, manager of the Firefox front-end features team.

We’re in the middle of the second great browser renaissance, and Firefox is no longer the sole leader. Feature-wise, Apple’s Safari browser is neck and neck with Firefox. Internet Explorer is catching up quickly. Google released its Chrome browser in September 2008. Much like Firefox, it arrived with a huge fanfare and quickly proved to be the web’s new golden child — simpler, faster, better than everyone else.

Along with Chrome, Google launched a public relations campaign highlighting the benefits of using its browser to run web applications like Gmail and Google Docs. Google’s PR push underscored the importance of things like browser performance and speed among developers and the general public alike.

In short, Google brought sexy back to the browser.

“One of the things Chrome did is make the way everybody communicates about browser development more energetic and public,” Vukićević says. “Before Chrome, we were doing a lot of really interesting things, but we were having a hard time communicating that.”

Nightingale agrees that since then, Mozilla has gotten a lot better at building up excitement around new features in Firefox. The company has launched a Hacks blog that shows demos of all the latest technologies, and it posts videos — sometimes as many as three or four per week — showcasing the innovations coming out of its experimental Labs office.

“Compared to the world that just had IE6 in it, we’re able to generate excitement about what we offer much more clearly,” Nightingale says.

In response to the increased interest in new technologies, Mozilla has stepped up its release schedule, too. The wait between Firefox 2 and Firefox 3 was close to two years — an eon in web time.

“When Firefox 3 neared completion, people were tremendously Angsty that it was such a superior experience to Firefox 2, yet we hadn’t shipped it yet,” Nightingale says. “That’s what stung the most. There were all these great features, and we weren’t ready to give it to people yet. We had to change that.”

Mozilla took another year to push out Firefox version 3.5, which arrived in June. But now, the team is committed to delivering a new release every six months. Firefox 3.6 is due by the end of 2009.

“We can’t have another two years where we’re sitting on awesome stuff that the rest of the world doesn’t get to have,” Nightingale says.

Another cause for Angst around the release of Firefox 3 was its abundance of features, which some users saw as unnecessary bloat. Version 3 fixed many of the stability and performance problems of its predecessor, but Firefox’s transformation from 2004’s svelte browser to today’s full-bodied machine was only made more obvious by Chrome’s debut as a bare-bones speed demon.

Still, Chrome’s arrival has put increased support for open web technologies on everyone’s road map. The next versions of Firefox will continue down that path.

At the top of the list for Firefox’s future is better support for HTML5, the set of technologies — already heavily supported by Firefox, Chrome and Safari (but not IE) — that define how web pages are built and how web applications function. Also, Mozilla has thrown its weight behind two open source technologies, the Web Open Font Format (WOFF) and the Ogg Theora video format. Both enable new methods for displaying fonts on web pages and for playing videos in the browser which don’t rely on proprietary technologies like Microsoft’s Silverlight and Adobe’s Flash and AIR.

This commitment to tools that let developers build better web experiences without using plug-ins was one of the project’s core principles when it was first launched.

According to Nightingale, openness will continue to play a key role in shaping the browser’s future.

“We always ask, ‘What is it that people on the open web can’t do right now? What’s pushing them towards things like Adobe AIR and Silverlight, or other technologies that are single-vendor silos?”

When a developer loses the ability to view a web page’s source code (something you can’t easily do in Flash) they can’t see how web applications and complex interactions function. And, he says, that stymies further experimentation.

“The web is going to be an awesome place to innovate in five years, because we’re going to chase down every awesome development in the proprietary world and make sure it happens on the open web as well. If we fail, then we’ll end up in a place that’s less recognizable than the web today, a web filled with a bunch of internet-delivered Flash executables.”

See Also:



Google Releases Closure JavaScript Tools For Building Slick Interfaces

Now, you can do the same crazy user interface stuff Google does on sites like Gmail and Google Docs on your own website.

The company announced it is releasing its Closure toolset under and open-source license on Thursday. The core pieces are the Closure Library, which contains the actual scripts themselves, the Closure Compiler, which optimizes and compresses the JavaScript code and the Closure Templates, which are pre-built templates for elements you can snap together to build your website’s interface. There’s also a JavaScript inspector.

It’s often hard to remember, but when Gmail first arrived on the scene in 2004, it was something entirely new. Ajax wasn’t as widely used yet, and Gmail showed off what a JavaScript-powered web app could do in a simple and straightforward way. Not only was it a great productivity tool, but the way it refreshed and allowed drag-and-drop seemed, to many of us, like magic. It turned the webmail inbox — and the web app rule book — upside down.

You can go to Google’s Code blog to read about Closure’s release, inspect the license and download the tools.

From the post:

Closure Compiler, Closure Library, Closure Templates, and Closure Inspector all started as 20% projects and hundreds of Googlers have contributed thousands of patches. Today, each Closure Tool has grown to be a key part of the JavaScript infrastructure behind web apps at Google.  That’s why we’re particularly excited (and humbled) to open source them to encourage and support web development outside Google. We want to hear what you think, but more importantly, we want to see what you make. So have at it and have fun!



Update Moves Weave Closer to a Starring Role in Firefox

Mozilla has updated Weave, its free add-on for Firefox that syncs your personal data across multiple PCs. Weave 0.8 is a vast improvement over its predecessor, featuring a huge speed boost and a revamped user interface that makes Weave feel much more a part of Firefox rather than an experimental hack.

If you’d like to take Weave 0.8 for a spin, head over to the Mozilla Labs Weave page and grab the latest version.

The most obvious change in this release is the new integration with Firefox’s preference pane. Previous versions of Weave used the URL about:weave to provide an interface for signing in and controlling which types of data Weave will sync. It worked, but it was hardly the best interface we’ve seen. Enter Weave 0.8 which ditches the URL and moves Weave’s preferences to a preference pane, which, well, just makes sense.

The move also hints at Weave’s future — becoming a standard part of Firefox. Unlike most extensions, which get their own separate preference panes, Weave’s preferences are now in the main Firefox preferences panel under a new tab “Services.” Given that syncing between PCs is something many Firefox users would welcome (and now that Google has just added bookmark syncing to the latest beta of Chrome) it’s nice to see Weave moving in the direction of a true Firefox feature rather than a separate add-on.

The incremental download support that arrived in Weave 0.7 has been improved for this release and, from out testing, seems to have eliminated the occasional lags and freezes that plagued early version of Weave.

Mozilla’s release notes for this version also claim that incremental download function will give “explicit priority… to your most important data.” The developer roadmap offers a partial clue as to how Weave determines what’s important, claiming the new system is based on “interestingness,” with the most “interesting” items synchronized first. However, thus far, the exact details of how Weave determines what’s interesting remain a mystery.

One thing you won’t find in this release is the “Weave can sign you into this site” option in the URL bar. Previous versions of Weave supported syncing and auto-login for web-based accounts. However, while Weave will still sync passwords, the auto-login feature has been moved off to a new Account Manager add-on that will be developed separately from Weave. If you’re missing the old login feature in Weave, give the Secure Login add-on a try, it offers similar features.

Also note that, if you’ve set up your own server to host and sync your Weave data, you’ll need to upgrade the server software to work with the latest version of Weave.

While we’re already missing the auto-login features in previous version of Weave, the obviously snappier performance and the much nicer user interface still make Weave 0.8 well worth the upgrade.

See Also:



Google Dashboard: One Service to Rule Them All

If you’ve ever wanted to see all the Google services you use — and how you’re using them — in one spot, then the new Google Dashboard is exactly what you’ve been looking for.

Google Dashboard is a one-stop shop for browsing through of almost all the Google services you’re using and, by extension, shows you everything Google knows about you. The nice thing about the new dashboard is that it gives you central way to manage and control that data — change privacy settings, control sharing and limit what data Google stores about you.

Each service listed in your dashboard contains an overview of your usage and links to change any data-sharing settings, edit any associated profiles and control who can see what. For example, the Google Reader entry in the dashboard shows a summary of your feeds, starred items and followers, and includes handy links to control your sharing settings.

There’s nothing in dashboard that can’t be found within the individual services themselves, but navigating through dashboard is considerably easier than trying to do the same on a service-by-service basis.

That said, Dashboard has a few quirks. For example my dashboard says I’m sharing a photo album on Orkut, but in fact it’s just the default album associated with my Orkut account, and it doesn’t actually have an photos in it. Ditto for my Picasa account.

Dashboard doesn’t currently offer any transparency about how your data is being used by Google for advertising or user-behavior data-collection purposes. It also offers little info about how (or how long) your data is being stored. It would also be nice if the Dashboard gave you a nice link to export all your data for each Google service. Eventually we’re hoping Google’s Data Liberation Front will fix that oversight and integrate some exporting tools directly into Dashboard.

Dashboard doesn’t currently support every Google service, though it does cover the most popular tools. The big omissions are Maps and Groups, though Dashboard does at least offer links to the services it doesn’t track.

To access the new Dashboard features, just click the My Account link in any Google service and then look for the new Dashboard link. Alternately you can head directly to the new Dashboard URL: https://www.google.com/dashboard.

To see Dashboard in action, check out the following video from Google:

See Also:



Tim Berners-Lee Sees Promise, Challenges in HTML5


SANTA CLARA, California — The man credited with founding the world wide web is both excited and cautious about its future.

Sir Tim Berners-Lee, the British physicist who first designed the way web servers deliver pages to web browsers nearly 19 years ago, sees great promise in HTML5, the much-anticipated rewrite of the language used to build web pages.

“I think (HTML5) is great,” he said at the Worldwide Web Consortium’s (W3C) annual member gathering, taking place here this week.

HTML5 is a mixture of several different technologies that allow content creators to do more with web pages. It defines rules for presenting video, audio, mathematical equations, complex layouts, 2-D animations and non-standard typefaces. Each bit of technology has its own working group within the W3C chartered with developing that one component.

“We’ve had the pieces for a while,” he says. “Seeing all these things finally coming together is exciting, and it multiplies the power of each one,” Berners-Lee says.

HTML5 also enhances the way browsers can store and process data, which has led to the creation of more complex and rich web applications that run in the browser like Gmail, Facebook and apps that allow real-time data sharing, like Google Wave.

“Yes, this is a markup language for web pages,” he says, “but the really big shift that’s happening here — and, you could argue, what’s actually driving the fancy features — is the shift to the web becoming a client-side computing platform.”

The HTML5 specification is close to completion. The most recent releases of browsers like Firefox, Chrome, Safari and Opera all support most of the technologies being rolled in to HTML5. Microsoft’s Internet Explorer supports fewer of HTML5’s advancements, but it’s catching up. HTML5 is expected to become an official recommendation by late 2010 or 2011.

Now that the web has been elevated to a more powerful computing platform by HTML5, Berners-Lee says it has also given rise to complicated security issues.

“You got a piece of code from site A, and you’re person B running a browser you got from company C, and that code wants to access data stored with company E for the purposes of printing it on a printer owned by company D — How do you build that so that it’s not susceptible to all kinds of nasty attacks?”

“The technology is very exciting, but there’s actually a lot of work to do in these corridors to make it work on the real web in a secure way.”

See Also:



Discover Cool Photo Apps With Flickr’s New ‘App Garden’

Everyone has an app store these days. But of course, for Flickr, the photo sharing site that brought you rainbow vomiting Panda Bears, “store” is far too pedestrian. Which is why Flickr has launched a new App Garden.

The new Flickr App Garden consists of mobile, desktop, and online widgets that interact with Flickr and help you get more out of the site. Flickr already had an extensive list of such apps in its “Services” area, but the new App Garden is considerably simpler and makes find cool Flickr apps much easier.

Unlike the former app directory, which was a simple list, Flickr’s App Garden gives each app its own page where users can leave comments, tag apps and mark them as favorites. The ability to favorite an app means users now have a way to promote their favorites in the App Garden showcase. The app pages also look and feel just like a Flickr photo pages, which makes App Garden feel more like a part of Flickr than the old services directory ever did.

To make it even easier to discover cool apps, Flickr has also included tags on user’s photos which tell you what app the image was uploaded with, and then link back to that app in the new App Garden. If you don’t want others to know how you upload your photos, you can turn off the new tags in your account settings.

The result is that you can stumble across some very cool stuff like Suggestify, an app that allows you to geotag other people’s photos by suggesting a location to the photo’s owner. Following the tag “geotag” then led us to an interesting iPhone app, FlickrUp, which lets you geotag photos uploaded from the iPhone.

So far there’s no way for developers to charge for applications through the Flickr App Garden, though there are some non-free apps listed. Since actually download the apps you want — whether free or not — requires at trip to the developer’s own page, it seems that, at least for now, the App Garden is more a place to browse, not buy apps.

See Also:



Same as it Ever Was: The History of HTML is a Conversation, Not a Spec

Developer Mark Pilgrim has posted a fascinating look at how the HTML img tag came into existence. The history Pilgrim digs up — mailing list conversations between the creators of the first web browsers like Marc Andreessen and the webs early pioneers like Tim Berners-Lee — show that far from being a carefully planned specification, the lingua franca of the web evolved a bit like the early universe — out of a murky chaos.

That from the chaos we got a workable — some would argue good — solution for creating the web is proof on some level that conversations and not abstracts, proposals and design by committee are the key to HTML’s success.

As Pilgrim writes:

HTML has always been a conversation between browser makers, authors, standards wonks, and other people who just showed up and liked to talk about angle brackets. Most of the successful versions of HTML have been “retro-specs,” catching up to the world while simultaneously trying to nudge it in the right direction.

You might be wondering, why did img succeed where other proposals, like an include or an icon tag failed? The answer is simple, because Marc Andreessen shipped code — Netscape Navigator — while those backing the other proposals, for most part, did not.

Of course that doesn’t mean that just shipping code is always good plan. Shipping code before a standard doesn’t necessarily produce the best solutions, as Pilgrim says. Or, put another way by a commentator on Pilgrim’s post, “shipping doesn’t mean you win, but not shipping means you lose.”

From those who shipped without the official blessing of a standard, we’ve come to have an img tag, the basis for AJAX, all of the HTML5 tools available in browsers today and much more.

Critics of HTML’s disorganized evolution will be quick to note that we’ve also come to have the blink tag, cross-browser rendering issues and other pains of web development.

Indeed we’re not suggesting that shipping features without at least engaging in the conversation is a good idea, but, when it comes to the future of HTML, if browser makers don’t ship HTML5 features before the standard is official we’ll be waiting until 2022 to use the new tools.

But while the future of HTML5 might be moving at a rather slow and convoluted pace. Pilgrim’s post is reminder that HTML has always progressed that way.

Perhaps the truly remarkable part is that, for all its flaws and convoluted evolution the core tech behind the web remains essentially the same now as it was then. “HTML is an unbroken line… a twisted, knotted, snarled line, to be sure… but still… Here we are, in 2009, and web pages from 1990 still render in modern browsers.”

See Also:



Firefox 3.6 Beta 1 Arrives: More Speed, Better Video, New Tab Tricks

Mozilla has unleashed the first beta release of Firefox 3.6, the next version of the popular open-source browser.

On the surface, it looks like incremental performance upgrade from the current version, Firefox 3.5, which was released in June. But anyone spending a great deal of time in JavaScript-heavy web apps — which these days is most of us — will notice faster page loads thanks to improvements to the browser’s rendering engine. This new beta also has better support for the latest emerging web standards like HTML5 and CSS3, better native video playback, a new plugin updating mechanism and some new tab behaviors.

If you’d like to test Firefox 3.6 beta 1, head over to the Mozilla downloads site and grab a copy. The final version is set to arrive sometime before the end of 2009. The relatively short six-month wait between upgrades is evidence of Mozilla’s promise to speed up its release schedule.Mozilla has slightly tweaked the way beta releases work. Now, if you download the beta, it will automatically upgrade to the release candidate, then the final release when it arrives.

One of the first things you’ll notice in the new beta is the performance boost. Firefox 3.6 features some tweaks to TraceMonkey, Mozilla’s own engine for rendering JavaScript on web pages . The new version of TraceMonkey in this release has been optimized to work within Firefox, meaning that, not only is TraceMonkey being used to speed up web apps, it’s now available to speed up Firefox UI elements written in JavaScript. That change should make the Firefox interface slightly snappier, and when combined with the new version of Gecko, Firefox’s core rendering engine, expect to some noticeable improvements in Firefox’s performance.

Mozilla hasn’t made any specific claims of speed boosts in Firefox 3.6, but in our testing, JavaScript-heavy sites like FriendFeed, Facebook and Gmail loaded faster, and the browser’s initial start-up time was much better than with Firefox 3.5 (especially if you’re reopening a large number of tabs).

But as with previously releases, Firefox loves to gobble up RAM. Perhaps not as much as pre-3.0 releases, but 3.6 still demands more overhead than Safari and Opera on our Macbook Pro.

The full screen support for native video embeds, which we told you about earlier this year, has arrived with the new beta. Just right click a video embedded using the HTML5 video tag and you’ll see a new menu item for full screen playback.

On the user interface front, the default tab behavior has been tweaked slightly. Opening a link by CMD-clicking now places the new tab right next to the currently open tab. That’s a significant change from previous versions, where the default behavior was to open new tabs at the far right side of the current window. Indeed if you just open a blank tab, it will be placed on the far right, but opening a link in a new tab will not.

Quite frankly, we found the new behavior frustrating and confounding — so much so that we’re unsure whether to call it a feature or a bug. Fortunately, there’s an easy way to get the old behavior back: head toabout:config and change the tabs.insertRelatedAfterCurrent setting to false.

Note: See Wired’s How-To Wiki entry on customizing Firefox 3.6 to add your own tips.

Also new on the tab front are the long-awaited preview thumbnails in Firefox’s built-in tab switcher, which have finally arrived — sort of. The tab previews have been in the works for quite some time and sadly, enabling the previews will still require a trip to about:config (set browser.ctrlTab.previews to true). Hopefully, by the time the final release arrives, preview icons on Firefox’s tab switcher will be turned on by default.

Firefox’s new tab-switching interface. Click the image for a larger view.

Firefox 3.6 beta 1 also supports Windows 7’s Aero Peek tab previews — the page and tab previews available in the Windows 7 task bar. As with other Win 7 apps, hovering your mouse over Firefox’s task bar icon will pop up previews of all your Firefox windows and tabs, making it quicker and easier to navigate between them.

Firefox 3.6 beta 1 brings built-in support for lightweight themes, which Mozilla calls Personas. Personas has been around for a while (you can even sync them through Weave), but previously installing Personas required a separate extension to manage them.

As of the new beta, Personas can be installed right out of the box, allowing you to tweak and theme Firefox as you’d like. Although Personas don’t offer quite the options of a full fledged theme, they’re much easier to create and install. If you’d like to try out some custom themes, head over to the Persona site.

The beta also features a new plug-in update mechanism which will warn you when, for example, your Flash plug-in is out of date and possibly vulnerable to attack.

Also new under the hood is the Web Open Font Format (WOFF) support we mentioned last month, as well as the new about:support page which offers a simple place to look up all the pertinent information about the current Firefox installation, including a list off installed extensions, any user-modified preference setting, links to installed plug-ins and other configuration details.

Read the full release notes if you want to see more about the nitty gritty bits.

As with any beta Firefox release, don’t expect all your favorite extensions to work right now. In our testing, Ad Block Plus and Weave were the only of our half dozen extensions that worked out of the box. You can help out add-on developers by grabbing the Add-on Compatibility Reporter, which will run all your extensions even if they haven’t been updated. Any resulting bugs or strange behaviors can be easily reported to the developers through the Add-ons Manager.

See Also:



Google Groups Fail: JQuery Dumps Google Over Spam, Interface Problems

Much of Google’s success rests on the fact that the words “Google” and “suck” rarely appear in the same sentence.

There is one notable exception: Google Groups, which lately has started to look more and more like an abandoned service. The mailing-list and discussion-board service has remained short on features since Google launched it in 2001. Meanwhile, Groups has become overwhelmed with spam, and one the most popular Google Groups — the JQuery mailing list, with more than 20,000 members — is jumping ship.

John Resig, the lead developer of JQuery, a popular JavaScript Library for developing complex web applications, recently posted a sharply critical look at Google Groups.

“As far as I’m concerned, Google Groups is dead,” he writes.

Resig isn’t the only one with problems. Google Groups began life as a way to rescue the Deja.com Usenet archive, but as our Epicenter blog recently reported, the Usenet portion of Google Groups is fundamentally broken. Google has since addressed some problems highlighted in that piece, but even newly created groups, like the JQuery group, feel neglected and overrun with spam.

While Resig is careful to note that Google Groups remains a workable optionfor private mailing lists, but for large public mailing lists like JQuery, Google Groups’ inability to combat spam, its poor moderator tools and general neglect have made the platform unusable.

“The problem mostly lies in the use cases that we’re trying to support,” Resig says in an e-mail to Webmonkey. “We need to support people who are actively trying to help new users, and we also need to support people who just want a simple question answered.” Spam, awkward filtering tools and a lack of support have driven JQuery to look elsewhere for a platform that connects its users, he says.

From an end-user point of view, the problem might not be immediately noticeable, especially if you’re using a good e-mail client which can filter out the spam for you. However, it can be a bit shocking to visit your favorite Groups’ homepage and discover it’s been overrun by spammers.

While Gmail is good at filtering spam, Google Groups is so bad, it’s almost as if the company isn’t even trying. There is a moderation option, which helps a bit. For example, compare the Django Users Group homepage (which uses moderation) to the EveryBlock Group (which doesn’t use moderation). As you can see, there isn’t one legitimate message on the Everyblock Group homepage, while there’s hardly any spam in the Django Group.

Sadly, as Resig points out, moderation makes joining and posting to a Google Group much more complex for the first-time users who have come seeking help, and the tools provided for moderators aren’t nearly as slick as you’d expect from a Google product.

Compounding the problem, spammers have figured out that spoofing e-mail addresses works swimmingly in Google Groups. So even with moderation turned on, spam will inevitably get through. Even worse, it’ll look like it came from legitimate list members, or even the moderators. In the end, the moderators have to moderate their own e-mail addresses to truly stop Google Groups spam.

Resig tells Webmonkey that JQuery is still looking for a suitable replacement for Google Groups. The top contenders are Vanilla Forums, which allows people to subscribe to all new posts and comments by e-mail, and Stack Exchange, which is essentially Stack Overflow customized for a specific topic.

Unfortunately, based on Resig’s account, it looks like Google’s Data Liberation Front hasn’t trained its data-export vision on Groups just yet — there is no way to export all the messages from a Group (there is, however, the ability to export a list of all members). In the JQuery Group’s case, that means some 120,000 messages in the group will have to exported by hand.

As for the future of Google Groups, well, the handwriting might well be on the wall. As blogger and former Yahoo engineer Andy Baio points out, “If you want to know which areas of big companies are being ignored, watch for spam taking over.”

See Also:



 
Subscribe now

Special Offer For Webmonkey Users

WIRED magazine:
The first word on how technology is changing our world.

Subscribe for just $10 a year